Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd51ca0333ec4f6ee31af4436b378b75035a89911d6fcea5f7562b6826495239

Tx prefix hash: 7d1d0e5b3924778145359e33e46ce0aafc52211fd5adcd8df44b4c5af96b8cbc
Tx public key: c09933f143c75b1ecf8a33f4ad17ac3f415e1a764ca3dbb341dc17bc61e36419
Timestamp: 1734760958 Timestamp [UCT]: 2024-12-21 06:02:38 Age [y:d:h:m:s]: 00:015:00:37:47
Block: 1179843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10728 RingCT/type: yes/0
Extra: 01c09933f143c75b1ecf8a33f4ad17ac3f415e1a764ca3dbb341dc17bc61e36419021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f4760193b70b81a1cff9595ec206f28495f877091cce89b9c837d26b37692cb 0.600000000000 1666242 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": 1179853, "vin": [ { "gen": { "height": 1179843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f4760193b70b81a1cff9595ec206f28495f877091cce89b9c837d26b37692cb" } } ], "extra": [ 1, 192, 153, 51, 241, 67, 199, 91, 30, 207, 138, 51, 244, 173, 23, 172, 63, 65, 94, 26, 118, 76, 163, 219, 179, 65, 220, 23, 188, 97, 227, 100, 25, 2, 17, 0, 0, 0, 3, 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