Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e80ab67bdd2ee5fb94896da75c6a4bf3ceecc1cd176837429aff51ba8da078d1

Tx prefix hash: f210b7535c80dda8da3ff3155697cbf654473abadcb8af7ae23c5bb1bb5cec6a
Tx public key: 8b3590c19e65bb9e2ce9199119ecf759d860f8ce0e7c7cf03195707b12d5c5b0
Timestamp: 1738697629 Timestamp [UCT]: 2025-02-04 19:33:49 Age [y:d:h:m:s]: 00:290:04:54:18
Block: 1212130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205177 RingCT/type: yes/0
Extra: 018b3590c19e65bb9e2ce9199119ecf759d860f8ce0e7c7cf03195707b12d5c5b002110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 280ebd9809cf17ee89afb23617717cb9d72938c9e54c33d06f667c4b293e238f 0.600000000000 1698899 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": 1212140, "vin": [ { "gen": { "height": 1212130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "280ebd9809cf17ee89afb23617717cb9d72938c9e54c33d06f667c4b293e238f" } } ], "extra": [ 1, 139, 53, 144, 193, 158, 101, 187, 158, 44, 233, 25, 145, 25, 236, 247, 89, 216, 96, 248, 206, 14, 124, 124, 240, 49, 149, 112, 123, 18, 213, 197, 176, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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