Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffdd04f28871ae72a19abbd29ca5c93632650ed684acff07817daa518bd8a444

Tx prefix hash: e9643dd4c6bc3a5d5eba483f7f94e653035f6607dac2907da03fc44ce4c87b3a
Tx public key: 39ebd3cf8757fdf8816a7d966b56afff256b1bd4d488c3a248ba7850dcc44574
Timestamp: 1698646596 Timestamp [UCT]: 2023-10-30 06:16:36 Age [y:d:h:m:s]: 01:094:04:25:32
Block: 880734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328286 RingCT/type: yes/0
Extra: 0139ebd3cf8757fdf8816a7d966b56afff256b1bd4d488c3a248ba7850dcc44574021100000007faf35c9c000000000000000000

1 output(s) for total of 0.740905228000 dcy

stealth address amount amount idx
00: 516215edf3d076d38a07a1cbd2cdcbf384f1c857e2d66a72caa244884f5b8453 0.740905228000 1336300 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": 880744, "vin": [ { "gen": { "height": 880734 } } ], "vout": [ { "amount": 740905228, "target": { "key": "516215edf3d076d38a07a1cbd2cdcbf384f1c857e2d66a72caa244884f5b8453" } } ], "extra": [ 1, 57, 235, 211, 207, 135, 87, 253, 248, 129, 106, 125, 150, 107, 86, 175, 255, 37, 107, 27, 212, 212, 136, 195, 162, 72, 186, 120, 80, 220, 196, 69, 116, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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