Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 240500e5e75427d36abfa68a8624366f6cbf93a70d454ce5a8fd13e2b88226bc

Tx prefix hash: da67e6bade8c7ee399a8f991ae03362edf3d046401a26def62c2ee4abebdc36d
Tx public key: 0d3460eaa93f0c0003326c1d379d6ad37536f56bbeb231eea3af2054589e0acb
Timestamp: 1702093559 Timestamp [UCT]: 2023-12-09 03:45:59 Age [y:d:h:m:s]: 01:038:01:18:02
Block: 909096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288560 RingCT/type: yes/0
Extra: 010d3460eaa93f0c0003326c1d379d6ad37536f56bbeb231eea3af2054589e0acb0211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2b140fe45efc1db9de37d1d6b91c47696435d76d12c3aa1285bf92dc828d667 0.600000000000 1366161 of 15

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": 909106, "vin": [ { "gen": { "height": 909096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2b140fe45efc1db9de37d1d6b91c47696435d76d12c3aa1285bf92dc828d667" } } ], "extra": [ 1, 13, 52, 96, 234, 169, 63, 12, 0, 3, 50, 108, 29, 55, 157, 106, 211, 117, 54, 245, 107, 190, 178, 49, 238, 163, 175, 32, 84, 88, 158, 10, 203, 2, 17, 0, 0, 0, 1, 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