Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d3d321271ae2bd500028f150cf22020434300f83dbf182c55013c1b1930d44a

Tx prefix hash: 25a35abbeafb3569e792303777ed06c64171daa0ef1c89740cda35f7c674ea43
Tx public key: 58817f8fc5c5f0789b644c7694cf1f839e1882ca379813bef2f38805f1e9dce0
Timestamp: 1699632815 Timestamp [UCT]: 2023-11-10 16:13:35 Age [y:d:h:m:s]: 01:143:22:42:10
Block: 888710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364063 RingCT/type: yes/0
Extra: 0158817f8fc5c5f0789b644c7694cf1f839e1882ca379813bef2f38805f1e9dce002110000000475e3f0e9000000000000000000

1 output(s) for total of 0.697163833000 dcy

stealth address amount amount idx
00: 9706ea824b5a415fd5baf6e83f0668d3cee86efb594af986dac9cc8a8ced2ae3 0.697163833000 1344665 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": 888720, "vin": [ { "gen": { "height": 888710 } } ], "vout": [ { "amount": 697163833, "target": { "key": "9706ea824b5a415fd5baf6e83f0668d3cee86efb594af986dac9cc8a8ced2ae3" } } ], "extra": [ 1, 88, 129, 127, 143, 197, 197, 240, 120, 155, 100, 76, 118, 148, 207, 31, 131, 158, 24, 130, 202, 55, 152, 19, 190, 242, 243, 136, 5, 241, 233, 220, 224, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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