Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0a285bc0ec1b8563214e8169c57633049eb8df3d821915233418739c59d0e1d

Tx prefix hash: 16e9f7ef4d7848e3acf8a565a28aab119a774c9214c32c8c96bec4405ae5b548
Tx public key: 5beeaa3d3a6af193cf0a84384b5fe8b31e9d6b095863949f416ecda66b55d5ca
Timestamp: 1718192722 Timestamp [UCT]: 2024-06-12 11:45:22 Age [y:d:h:m:s]: 00:297:02:13:33
Block: 1042581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212300 RingCT/type: yes/0
Extra: 015beeaa3d3a6af193cf0a84384b5fe8b31e9d6b095863949f416ecda66b55d5ca0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a97716750cfd4d2b2b616adeb863e25b625efb6b56e2d50904491b5597ca449 0.600000000000 1511526 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": 1042591, "vin": [ { "gen": { "height": 1042581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a97716750cfd4d2b2b616adeb863e25b625efb6b56e2d50904491b5597ca449" } } ], "extra": [ 1, 91, 238, 170, 61, 58, 106, 241, 147, 207, 10, 132, 56, 75, 95, 232, 179, 30, 157, 107, 9, 88, 99, 148, 159, 65, 110, 205, 166, 107, 85, 213, 202, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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