Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1a425f1f706a7be6bca500317cfddc81a237a21ee498c721734a948158a602a

Tx prefix hash: d4422f01d2d96f619182fb01daac1082d8fda38b90cc89be38e7d576b01f5bd1
Tx public key: cbe706a379e92a99c0557789d3606a51badc33d91fedb6af553f78184024695a
Timestamp: 1685541783 Timestamp [UCT]: 2023-05-31 14:03:03 Age [y:d:h:m:s]: 01:168:11:47:17
Block: 772131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381789 RingCT/type: yes/0
Extra: 01cbe706a379e92a99c0557789d3606a51badc33d91fedb6af553f78184024695a021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.696717897000 dcy

stealth address amount amount idx
00: 6d6e5d7105dbc29ef6e1e3e74c1651f8611680d58b093670d70c1a62d39f7bc4 1.696717897000 1221522 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": 772141, "vin": [ { "gen": { "height": 772131 } } ], "vout": [ { "amount": 1696717897, "target": { "key": "6d6e5d7105dbc29ef6e1e3e74c1651f8611680d58b093670d70c1a62d39f7bc4" } } ], "extra": [ 1, 203, 231, 6, 163, 121, 233, 42, 153, 192, 85, 119, 137, 211, 96, 106, 81, 186, 220, 51, 217, 31, 237, 182, 175, 85, 63, 120, 24, 64, 36, 105, 90, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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