Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d28a31656289d12b182f5ccf6f3dbf6e00005e34473b7697c1db2428f15ae60

Tx prefix hash: 05159c4330934a1da0bbf3479ec4f904fd206578187b55c268571c0d49064ff2
Tx public key: d72b8a985eeb5e09332f2dc1552d01e46a61c934387a82b4884a303a13911458
Timestamp: 1682587533 Timestamp [UCT]: 2023-04-27 09:25:33 Age [y:d:h:m:s]: 01:156:18:38:11
Block: 747636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373502 RingCT/type: yes/0
Extra: 01d72b8a985eeb5e09332f2dc1552d01e46a61c934387a82b4884a303a1391145802110000000133af99f4000000000000000000

1 output(s) for total of 2.045369521000 dcy

stealth address amount amount idx
00: d86d9779e9f64c3f5a9b0dca9d4f098243f21ddda8a9ca45d3593eeae062b684 2.045369521000 1195355 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": 747646, "vin": [ { "gen": { "height": 747636 } } ], "vout": [ { "amount": 2045369521, "target": { "key": "d86d9779e9f64c3f5a9b0dca9d4f098243f21ddda8a9ca45d3593eeae062b684" } } ], "extra": [ 1, 215, 43, 138, 152, 94, 235, 94, 9, 51, 47, 45, 193, 85, 45, 1, 228, 106, 97, 201, 52, 56, 122, 130, 180, 136, 74, 48, 58, 19, 145, 20, 88, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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