Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e183490697d052de9c1c35d1acda670c11d765de9910b2dee2406a9dc780a163

Tx prefix hash: f669b2360b3a4291a832551518813caef6aadcedd8a97da7bbf9341fc3902809
Tx public key: 6a8616b64f63dbb697d539ccf2dbcb4d4563f21b6d8f9ed0c4a75b63339e3379
Timestamp: 1706740058 Timestamp [UCT]: 2024-01-31 22:27:38 Age [y:d:h:m:s]: 01:136:00:04:17
Block: 947605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358226 RingCT/type: yes/0
Extra: 016a8616b64f63dbb697d539ccf2dbcb4d4563f21b6d8f9ed0c4a75b63339e33790211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6552f8b87634ccc7c6d86e1beab0a08d5bca7f2640c264701a03f1afef0c6fc6 0.600000000000 1405961 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": 947615, "vin": [ { "gen": { "height": 947605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6552f8b87634ccc7c6d86e1beab0a08d5bca7f2640c264701a03f1afef0c6fc6" } } ], "extra": [ 1, 106, 134, 22, 182, 79, 99, 219, 182, 151, 213, 57, 204, 242, 219, 203, 77, 69, 99, 242, 27, 109, 143, 158, 208, 196, 167, 91, 99, 51, 158, 51, 121, 2, 17, 0, 0, 0, 6, 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