Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f517c178f7d9c246f495e8c1c0502f94a7ffa805922df42c1cef1381d90e7be

Tx prefix hash: 8892042bc652a64bc43ad2df75206cbe93e98d7064795a334dafd621b388a5a9
Tx public key: ed0dbc0e31392baf7ebc0d76ef6abeaa371b33ec5e1ee6f02dfb552980919529
Timestamp: 1687195200 Timestamp [UCT]: 2023-06-19 17:20:00 Age [y:d:h:m:s]: 01:299:17:53:33
Block: 785838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475409 RingCT/type: yes/0
Extra: 01ed0dbc0e31392baf7ebc0d76ef6abeaa371b33ec5e1ee6f02dfb55298091952902110000000283600029000000000000000000

1 output(s) for total of 1.528243790000 dcy

stealth address amount amount idx
00: d2d5db683b8f089ebae17a853ddad9cc2c37f4ab09b6ee6f90234024602d6941 1.528243790000 1235811 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": 785848, "vin": [ { "gen": { "height": 785838 } } ], "vout": [ { "amount": 1528243790, "target": { "key": "d2d5db683b8f089ebae17a853ddad9cc2c37f4ab09b6ee6f90234024602d6941" } } ], "extra": [ 1, 237, 13, 188, 14, 49, 57, 43, 175, 126, 188, 13, 118, 239, 106, 190, 170, 55, 27, 51, 236, 94, 30, 230, 240, 45, 251, 85, 41, 128, 145, 149, 41, 2, 17, 0, 0, 0, 2, 131, 96, 0, 41, 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