Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06c3153fcc26068e4e14232093a398b524dc641d55016dd92478fb69364c1b08

Tx prefix hash: 40d0c87ee27b1e04328ba1fc35bd7c8fb1398b17744bb636b531ec046d6b585d
Tx public key: 2d5f6bf827ff74d6bea7babf8894e115a46ac1b1a0509b30bb1cba52af1a0065
Timestamp: 1741273121 Timestamp [UCT]: 2025-03-06 14:58:41 Age [y:d:h:m:s]: 00:093:12:23:43
Block: 1233464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66886 RingCT/type: yes/0
Extra: 012d5f6bf827ff74d6bea7babf8894e115a46ac1b1a0509b30bb1cba52af1a0065021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78fa1f639b0f392dd1395e0d40c8282b13a4254062ecd1c8877785de5e74c6b1 0.600000000000 1720385 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": 1233474, "vin": [ { "gen": { "height": 1233464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78fa1f639b0f392dd1395e0d40c8282b13a4254062ecd1c8877785de5e74c6b1" } } ], "extra": [ 1, 45, 95, 107, 248, 39, 255, 116, 214, 190, 167, 186, 191, 136, 148, 225, 21, 164, 106, 193, 177, 160, 80, 155, 48, 187, 28, 186, 82, 175, 26, 0, 101, 2, 17, 0, 0, 0, 5, 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