Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11ec2a9567c2b22d4345c52b8fedc185d78e1efa8d128a9611bab6ba86e893a2

Tx prefix hash: 6b53bfa3b00a8493a4afda0d351f00e681c2e3289e11d9c617749850fee83d24
Tx public key: 2803ec6d5771f40f28f0f4883f91f387f96035b1ce986fcab7f6f83fc735abb5
Timestamp: 1697410998 Timestamp [UCT]: 2023-10-15 23:03:18 Age [y:d:h:m:s]: 01:175:12:38:01
Block: 870486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386470 RingCT/type: yes/0
Extra: 012803ec6d5771f40f28f0f4883f91f387f96035b1ce986fcab7f6f83fc735abb502110000000275e3f0e9000000000000000000

1 output(s) for total of 0.801158699000 dcy

stealth address amount amount idx
00: 71091466cb7c45792f7eb9c92458b4d70f0509f8b5c54fab7648f10200257108 0.801158699000 1325365 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": 870496, "vin": [ { "gen": { "height": 870486 } } ], "vout": [ { "amount": 801158699, "target": { "key": "71091466cb7c45792f7eb9c92458b4d70f0509f8b5c54fab7648f10200257108" } } ], "extra": [ 1, 40, 3, 236, 109, 87, 113, 244, 15, 40, 240, 244, 136, 63, 145, 243, 135, 249, 96, 53, 177, 206, 152, 111, 202, 183, 246, 248, 63, 199, 53, 171, 181, 2, 17, 0, 0, 0, 2, 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