Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d75e473e35d887bad93029039dba057485b936528c199a3b49e23f1f662df7a

Tx prefix hash: 46291395dd8bc3f26a7ecdf4a1bd2640aaeb585c7e2a69c306c8e07a8f35bfd0
Tx public key: 6f2fb9cfa21494a4215ebd67198df95276c73e3cc58570080a6163c97fff3f88
Timestamp: 1677324692 Timestamp [UCT]: 2023-02-25 11:31:32 Age [y:d:h:m:s]: 01:281:02:59:36
Block: 704637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461831 RingCT/type: yes/0
Extra: 016f2fb9cfa21494a4215ebd67198df95276c73e3cc58570080a6163c97fff3f88021100000002835e4d22000000000000000000

1 output(s) for total of 2.839520554000 dcy

stealth address amount amount idx
00: 8d4d9a6e3570653d82bee38194ba9291e4baf0fa48dfad3832b551da1a5c609a 2.839520554000 1148308 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": 704647, "vin": [ { "gen": { "height": 704637 } } ], "vout": [ { "amount": 2839520554, "target": { "key": "8d4d9a6e3570653d82bee38194ba9291e4baf0fa48dfad3832b551da1a5c609a" } } ], "extra": [ 1, 111, 47, 185, 207, 162, 20, 148, 164, 33, 94, 189, 103, 25, 141, 249, 82, 118, 199, 62, 60, 197, 133, 112, 8, 10, 97, 99, 201, 127, 255, 63, 136, 2, 17, 0, 0, 0, 2, 131, 94, 77, 34, 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