Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9325a44ebf644d3bc1cfa542d2e67a4d984c1839e7ffa0d61456d87b5287db5b

Tx prefix hash: d35527980ab730d99b6743d45f0f21da58b3dab5c6ca309d49ca3e985618ebdb
Tx public key: dad66d4f23175570cffec04abc931c620bebe6f9b30d9948f12f1669697ad7f2
Timestamp: 1576643461 Timestamp [UCT]: 2019-12-18 04:31:01 Age [y:d:h:m:s]: 05:016:02:56:25
Block: 28231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1159488 RingCT/type: yes/0
Extra: 01dad66d4f23175570cffec04abc931c620bebe6f9b30d9948f12f1669697ad7f202110000005fad433a0b000000000000000000

1 output(s) for total of 494.834353571000 dcy

stealth address amount amount idx
00: 5efb0d18edd70de1a1477ce0f4fb8f25471c1392ae926a61d8e653a88aa37914 494.834353571000 46761 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": 28241, "vin": [ { "gen": { "height": 28231 } } ], "vout": [ { "amount": 494834353571, "target": { "key": "5efb0d18edd70de1a1477ce0f4fb8f25471c1392ae926a61d8e653a88aa37914" } } ], "extra": [ 1, 218, 214, 109, 79, 35, 23, 85, 112, 207, 254, 192, 74, 188, 147, 28, 98, 11, 235, 230, 249, 179, 13, 153, 72, 241, 47, 22, 105, 105, 122, 215, 242, 2, 17, 0, 0, 0, 95, 173, 67, 58, 11, 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