Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9650894293676afaa769d9d0303083b8bef4bb9eafc44ba5eef8cece8b0201ff

Tx prefix hash: 53a005cb624fb2802c03c9939af407c34d25fa16378ffc5c4d6a0f570aa64019
Tx public key: 051f8fac9e511c4cdf6915f1e9333eddff3ef5a770b6e7bf215507a074bb5078
Timestamp: 1706101788 Timestamp [UCT]: 2024-01-24 13:09:48 Age [y:d:h:m:s]: 01:344:22:41:22
Block: 942303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505430 RingCT/type: yes/0
Extra: 01051f8fac9e511c4cdf6915f1e9333eddff3ef5a770b6e7bf215507a074bb50780211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4500430bc7d9ac640e3ab909bfd56f2e3ecdfa0a5989d74bba93442197294e6 0.600000000000 1400473 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 942313, "vin": [ { "gen": { "height": 942303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4500430bc7d9ac640e3ab909bfd56f2e3ecdfa0a5989d74bba93442197294e6" } } ], "extra": [ 1, 5, 31, 143, 172, 158, 81, 28, 76, 223, 105, 21, 241, 233, 51, 62, 221, 255, 62, 245, 167, 112, 182, 231, 191, 33, 85, 7, 160, 116, 187, 80, 120, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8