Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b58920cbade3be45643a2e2e442254a511aee29de386ab4f4817b502b03e57b7

Tx prefix hash: 9900189f866d27cc21dbe6c824f81cd3950520c3d1c9e73ef72d3354bacaf97a
Tx public key: 68f05d95d1a9d7cb2f5aaf565f8fb07dbb3187fa720bbbed911456037dce7c3f
Timestamp: 1744598584 Timestamp [UCT]: 2025-04-14 02:43:04 Age [y:d:h:m:s]: 00:288:09:52:09
Block: 1261002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203747 RingCT/type: yes/0
Extra: 0168f05d95d1a9d7cb2f5aaf565f8fb07dbb3187fa720bbbed911456037dce7c3f0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c0e13b382d0a0fcb9ace079d94c64e24091e6c29c1e57089bfcabf29e62cc1b 0.600000000000 1748167 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": 1261012, "vin": [ { "gen": { "height": 1261002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c0e13b382d0a0fcb9ace079d94c64e24091e6c29c1e57089bfcabf29e62cc1b" } } ], "extra": [ 1, 104, 240, 93, 149, 209, 169, 215, 203, 47, 90, 175, 86, 95, 143, 176, 125, 187, 49, 135, 250, 114, 11, 187, 237, 145, 20, 86, 3, 125, 206, 124, 63, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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