Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df39689841e2d3ad1063cdda8c8fa379146b4a1849f056aa8272737089613e80

Tx prefix hash: e9cc8b9c10e1bbce5aa272674a85145aeabb6c0f22522c43df84881990770737
Tx public key: ef2eea2a8c3c91fdf8d5702c55bfa3ae3d2021254432873a66b7f3e6ad6cd1d3
Timestamp: 1640032446 Timestamp [UCT]: 2021-12-20 20:34:06 Age [y:d:h:m:s]: 03:315:12:45:09
Block: 399861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1001979 RingCT/type: yes/0
Extra: 01ef2eea2a8c3c91fdf8d5702c55bfa3ae3d2021254432873a66b7f3e6ad6cd1d3021100000001aee7c7be000000000000000000

1 output(s) for total of 29.046570861000 dcy

stealth address amount amount idx
00: 318c4bc182b1b2e9aa6677e715d1a9006ce2e89b300511fcd81219c3f95b9e81 29.046570861000 799141 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": 399871, "vin": [ { "gen": { "height": 399861 } } ], "vout": [ { "amount": 29046570861, "target": { "key": "318c4bc182b1b2e9aa6677e715d1a9006ce2e89b300511fcd81219c3f95b9e81" } } ], "extra": [ 1, 239, 46, 234, 42, 140, 60, 145, 253, 248, 213, 112, 44, 85, 191, 163, 174, 61, 32, 33, 37, 68, 50, 135, 58, 102, 183, 243, 230, 173, 108, 209, 211, 2, 17, 0, 0, 0, 1, 174, 231, 199, 190, 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