Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34fccce116f6c2b8f5786ca3b806f1ff9bf6be8a6bc7d572f2ce55d82fd4692d

Tx prefix hash: be138f81b2ce66ade7b7e03ed2ff3aa2f7565b16694824e2f1e7e954bb639c0e
Tx public key: 0dd59de3832f2fae93146fd84076334965bc0fb50bfa112d923526cc3d8a1973
Timestamp: 1634700024 Timestamp [UCT]: 2021-10-20 03:20:24 Age [y:d:h:m:s]: 03:070:11:11:39
Block: 356589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 828471 RingCT/type: yes/0
Extra: 010dd59de3832f2fae93146fd84076334965bc0fb50bfa112d923526cc3d8a197302110000000afdc024ec000000000000000000

1 output(s) for total of 40.408527956000 dcy

stealth address amount amount idx
00: 58aa0ceac9065f924615e6429c51f5a5fd62136a0a5a06b8685827e6da4a4833 40.408527956000 727491 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": 356599, "vin": [ { "gen": { "height": 356589 } } ], "vout": [ { "amount": 40408527956, "target": { "key": "58aa0ceac9065f924615e6429c51f5a5fd62136a0a5a06b8685827e6da4a4833" } } ], "extra": [ 1, 13, 213, 157, 227, 131, 47, 47, 174, 147, 20, 111, 216, 64, 118, 51, 73, 101, 188, 15, 181, 11, 250, 17, 45, 146, 53, 38, 204, 61, 138, 25, 115, 2, 17, 0, 0, 0, 10, 253, 192, 36, 236, 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