Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f3721426aee91c78b87e292d7f46b6574db62a24bac8e8e898b55ead1f7dd9e

Tx prefix hash: 177966c272ea8c9dd57b5c81d8a5e22d121a9f1045388bd6ca0a7d27741c63c1
Tx public key: 5b7268be30e8c5962deb6c2429b75da09a5c4e507ab0daf20c87b094ef968dfb
Timestamp: 1741245390 Timestamp [UCT]: 2025-03-06 07:16:30 Age [y:d:h:m:s]: 00:308:11:12:42
Block: 1233228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218281 RingCT/type: yes/0
Extra: 015b7268be30e8c5962deb6c2429b75da09a5c4e507ab0daf20c87b094ef968dfb0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb8fa8ef1709718d1c6d4f0cf9ecd271b8ec9755fea742d4a954f85458b3e6fd 0.600000000000 1720147 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": 1233238, "vin": [ { "gen": { "height": 1233228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb8fa8ef1709718d1c6d4f0cf9ecd271b8ec9755fea742d4a954f85458b3e6fd" } } ], "extra": [ 1, 91, 114, 104, 190, 48, 232, 197, 150, 45, 235, 108, 36, 41, 183, 93, 160, 154, 92, 78, 80, 122, 176, 218, 242, 12, 135, 176, 148, 239, 150, 141, 251, 2, 17, 0, 0, 0, 2, 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