Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40d368c5a0a61394d36a09fb32c5449df69cea35984205f706fe66ee06beaa12

Tx prefix hash: efa1e65e2bdd7dd31429cae7f2445654e766b05ce9ae3df135e3ea50b64ba9bc
Tx public key: 000edecc3cc0719259f736a87978b3cd3b9ae903650c7437a8cb094ecb19af2f
Timestamp: 1737678037 Timestamp [UCT]: 2025-01-24 00:20:37 Age [y:d:h:m:s]: 00:146:11:52:38
Block: 1203919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104415 RingCT/type: yes/0
Extra: 01000edecc3cc0719259f736a87978b3cd3b9ae903650c7437a8cb094ecb19af2f02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b66eaa37b8afbb3c0c0600855aa92423831f11487deb2dca6f36cc0a3d3fcd6 0.600000000000 1690600 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": 1203929, "vin": [ { "gen": { "height": 1203919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b66eaa37b8afbb3c0c0600855aa92423831f11487deb2dca6f36cc0a3d3fcd6" } } ], "extra": [ 1, 0, 14, 222, 204, 60, 192, 113, 146, 89, 247, 54, 168, 121, 120, 179, 205, 59, 154, 233, 3, 101, 12, 116, 55, 168, 203, 9, 78, 203, 25, 175, 47, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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