Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5330c73174c7d8204a830fcf9dca6a0949d322e9cbd784a4849ac5051541f074

Tx prefix hash: d4f16b463b0813019338641dc54d45d209dd9a87a28ab608c1d0c23ec99c8e5b
Tx public key: 4d0590551b6bf7e8f9f099d3d6f278a02e15c36c6f46d3fe7d876a1450e58752
Timestamp: 1627574669 Timestamp [UCT]: 2021-07-29 16:04:29 Age [y:d:h:m:s]: 03:271:16:03:39
Block: 303254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 966479 RingCT/type: yes/0
Extra: 014d0590551b6bf7e8f9f099d3d6f278a02e15c36c6f46d3fe7d876a1450e5875202110000000901f1e57f000000000000000000

1 output(s) for total of 60.700755574000 dcy

stealth address amount amount idx
00: 51cd452ff0c4bbfd2185bb007d2b5eae39300dac739d6ca78a89d6ed18f1b651 60.700755574000 632979 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": 303264, "vin": [ { "gen": { "height": 303254 } } ], "vout": [ { "amount": 60700755574, "target": { "key": "51cd452ff0c4bbfd2185bb007d2b5eae39300dac739d6ca78a89d6ed18f1b651" } } ], "extra": [ 1, 77, 5, 144, 85, 27, 107, 247, 232, 249, 240, 153, 211, 214, 242, 120, 160, 46, 21, 195, 108, 111, 70, 211, 254, 125, 135, 106, 20, 80, 229, 135, 82, 2, 17, 0, 0, 0, 9, 1, 241, 229, 127, 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