Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 440f8e13703538e413ddce4b5b1fc3c354a76eec569ef3050325c86bba4420a6

Tx prefix hash: 7a036376e7f1bb2167a8beca738165ab687c5d2e3dd58c0b793cb08a46e2ff7f
Tx public key: addcb17d65e5001d42d543e2fbc3f80623b73e122337ee5ab81962ad4666bb78
Timestamp: 1684950090 Timestamp [UCT]: 2023-05-24 17:41:30 Age [y:d:h:m:s]: 01:192:04:59:50
Block: 767228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398773 RingCT/type: yes/0
Extra: 01addcb17d65e5001d42d543e2fbc3f80623b73e122337ee5ab81962ad4666bb7802110000000475e3f0e9000000000000000000

1 output(s) for total of 1.761479173000 dcy

stealth address amount amount idx
00: 29c706a56dd3aeebaedf80268c7e26acb8c4c7b309d55fe05c07b1afb8ace057 1.761479173000 1216341 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": 767238, "vin": [ { "gen": { "height": 767228 } } ], "vout": [ { "amount": 1761479173, "target": { "key": "29c706a56dd3aeebaedf80268c7e26acb8c4c7b309d55fe05c07b1afb8ace057" } } ], "extra": [ 1, 173, 220, 177, 125, 101, 229, 0, 29, 66, 213, 67, 226, 251, 195, 248, 6, 35, 183, 62, 18, 35, 55, 238, 90, 184, 25, 98, 173, 70, 102, 187, 120, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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