Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8ad47345ce61d9b7060b657b68a4c6841a37bd2d54a6c5d973ffa0d93456d67

Tx prefix hash: 8ddbddaf2f9fe582a2d87851daa64ccdfe6c6031144ac6998b0e8e54900da6e1
Tx public key: 7a81381ba2c37025b02706f0616df2fc844a0951998307f585bd318dae2f1c11
Timestamp: 1736162991 Timestamp [UCT]: 2025-01-06 11:29:51 Age [y:d:h:m:s]: 00:297:18:30:59
Block: 1191434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210302 RingCT/type: yes/0
Extra: 017a81381ba2c37025b02706f0616df2fc844a0951998307f585bd318dae2f1c110211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7988bffe4d9bce4475b65a1b0114ae11ae3a34ddbe34f48a8c862256c82e739 0.600000000000 1677971 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": 1191444, "vin": [ { "gen": { "height": 1191434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7988bffe4d9bce4475b65a1b0114ae11ae3a34ddbe34f48a8c862256c82e739" } } ], "extra": [ 1, 122, 129, 56, 27, 162, 195, 112, 37, 176, 39, 6, 240, 97, 109, 242, 252, 132, 74, 9, 81, 153, 131, 7, 245, 133, 189, 49, 141, 174, 47, 28, 17, 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