Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98905ea83919436f799384f0db74c239b11fe70d4d37c18f73b4be05621d9a12

Tx prefix hash: c50555a6c76cabe10b11e4fc0ff0e4340c2363e6f94ed5fa8847fb62e3d0fe47
Tx public key: 32fa1ba3ef07e8cbd3553ccf26064a025417f020a960496f8938c40e57a99d4f
Timestamp: 1743345134 Timestamp [UCT]: 2025-03-30 14:32:14 Age [y:d:h:m:s]: 00:228:07:35:33
Block: 1250604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160909 RingCT/type: yes/0
Extra: 0132fa1ba3ef07e8cbd3553ccf26064a025417f020a960496f8938c40e57a99d4f0211000000021a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c86b7e0c9b55a6d627fb7dc30fbac81e365c9e32e60902e4b40c3fbd7e144a30 0.600000000000 1737653 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": 1250614, "vin": [ { "gen": { "height": 1250604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c86b7e0c9b55a6d627fb7dc30fbac81e365c9e32e60902e4b40c3fbd7e144a30" } } ], "extra": [ 1, 50, 250, 27, 163, 239, 7, 232, 203, 211, 85, 60, 207, 38, 6, 74, 2, 84, 23, 240, 32, 169, 96, 73, 111, 137, 56, 196, 14, 87, 169, 157, 79, 2, 17, 0, 0, 0, 2, 26, 151, 4, 3, 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