Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b991fe071e5caf5e2c5bcaff4930c6eaf81ebd18e78b2a555738bbd4073195d

Tx prefix hash: bdba200b4ece5e1e04e448e5e322e7f67115f7b8d4a8f7c6ed65852c6412fd1d
Tx public key: 4ab609317ad94869e9ca7f0f7ceffe6f17121503c5993256461a766ecbd2ecf6
Timestamp: 1709962583 Timestamp [UCT]: 2024-03-09 05:36:23 Age [y:d:h:m:s]: 01:249:22:19:20
Block: 974347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437345 RingCT/type: yes/0
Extra: 014ab609317ad94869e9ca7f0f7ceffe6f17121503c5993256461a766ecbd2ecf602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 481609edf4c6bf40b2a81376391ae38c1aeef4f8d136561b7cac81b2a0804013 0.600000000000 1434302 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": 974357, "vin": [ { "gen": { "height": 974347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "481609edf4c6bf40b2a81376391ae38c1aeef4f8d136561b7cac81b2a0804013" } } ], "extra": [ 1, 74, 182, 9, 49, 122, 217, 72, 105, 233, 202, 127, 15, 124, 239, 254, 111, 23, 18, 21, 3, 197, 153, 50, 86, 70, 26, 118, 110, 203, 210, 236, 246, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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