Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19f1502e2b92d8621e210f95ae053c6060fd7cff050054c07e5f2c5262827348

Tx prefix hash: d51cefbb42f981228db597b3da75d3832ebb0778745c675cbb280bc0bf632eda
Tx public key: 351b5c88bbc31e14856e76aeedd7dc1a7a173e4d1f1c8797ff833f5af7316335
Timestamp: 1624984510 Timestamp [UCT]: 2021-06-29 16:35:10 Age [y:d:h:m:s]: 03:251:02:16:46
Block: 285361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 948216 RingCT/type: yes/0
Extra: 01351b5c88bbc31e14856e76aeedd7dc1a7a173e4d1f1c8797ff833f5af731633502110000000a15cf69a8000000000000000000

1 output(s) for total of 69.579460922000 dcy

stealth address amount amount idx
00: aaac5731e1b405d915bda523e504019da3bc5756c983f97395ba6959f9647af4 69.579460922000 597468 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": 285371, "vin": [ { "gen": { "height": 285361 } } ], "vout": [ { "amount": 69579460922, "target": { "key": "aaac5731e1b405d915bda523e504019da3bc5756c983f97395ba6959f9647af4" } } ], "extra": [ 1, 53, 27, 92, 136, 187, 195, 30, 20, 133, 110, 118, 174, 237, 215, 220, 26, 122, 23, 62, 77, 31, 28, 135, 151, 255, 131, 63, 90, 247, 49, 99, 53, 2, 17, 0, 0, 0, 10, 21, 207, 105, 168, 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