Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64fc6ae4fe685a836d64f93c9f81b921ec9b78dd632b3c8aa888b74d1dedc417

Tx prefix hash: d290530498699e5b350809de630b4248e410d1724491fb5bd2b2a617237fa12c
Tx public key: a7aa912ab6e5cc243af6d9545d2137798865c95097d1c9b0f6251bb603605244
Timestamp: 1694054342 Timestamp [UCT]: 2023-09-07 02:39:02 Age [y:d:h:m:s]: 01:221:20:34:21
Block: 842633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419679 RingCT/type: yes/0
Extra: 01a7aa912ab6e5cc243af6d9545d2137798865c95097d1c9b0f6251bb60360524402110000000a4b8f5122000000000000000000

1 output(s) for total of 0.990848246000 dcy

stealth address amount amount idx
00: cc236801393585b66fa7c3c69b25ab1633f7ac9a916d26960f09811a564fe294 0.990848246000 1295773 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": 842643, "vin": [ { "gen": { "height": 842633 } } ], "vout": [ { "amount": 990848246, "target": { "key": "cc236801393585b66fa7c3c69b25ab1633f7ac9a916d26960f09811a564fe294" } } ], "extra": [ 1, 167, 170, 145, 42, 182, 229, 204, 36, 58, 246, 217, 84, 93, 33, 55, 121, 136, 101, 201, 80, 151, 209, 201, 176, 246, 37, 27, 182, 3, 96, 82, 68, 2, 17, 0, 0, 0, 10, 75, 143, 81, 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