Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcb4b89d78b6beaebaacc1481fc0c6cf0598b1ef5ec7ede376e2148efe53c3e3

Tx prefix hash: d8e1ecfb3675ce536d273b94fdc35a60ec43376c5d1937670db5eb5c157a591c
Tx public key: 6d178dbacd08466416e7e2a830a4dd5b7a261f4268d264683acf3af6fe2d5a1a
Timestamp: 1651317968 Timestamp [UCT]: 2022-04-30 11:26:08 Age [y:d:h:m:s]: 02:363:00:09:54
Block: 491327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 779232 RingCT/type: yes/0
Extra: 016d178dbacd08466416e7e2a830a4dd5b7a261f4268d264683acf3af6fe2d5a1a02110000000a4da16a3a000000000000000000

1 output(s) for total of 14.455393143000 dcy

stealth address amount amount idx
00: cbf0961b7c5f6e0aac16562407392f62e7bf3d59e94ba3fc887d6e896d99120d 14.455393143000 914486 of 0

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": 491337, "vin": [ { "gen": { "height": 491327 } } ], "vout": [ { "amount": 14455393143, "target": { "key": "cbf0961b7c5f6e0aac16562407392f62e7bf3d59e94ba3fc887d6e896d99120d" } } ], "extra": [ 1, 109, 23, 141, 186, 205, 8, 70, 100, 22, 231, 226, 168, 48, 164, 221, 91, 122, 38, 31, 66, 104, 210, 100, 104, 58, 207, 58, 246, 254, 45, 90, 26, 2, 17, 0, 0, 0, 10, 77, 161, 106, 58, 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