Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ec3eca34443bcbebdd3865b7710afd3800a68e032bfe68e122969a6b90b45d8

Tx prefix hash: 54ae207eeb84ed991c91c7ae141ce38801a8854eb53a659275f724e3b7a9c849
Tx public key: 920708fba54b598dfb71b71a807c11b01a68c4d5c6fb7b868c815be64cdb5fcd
Timestamp: 1708964727 Timestamp [UCT]: 2024-02-26 16:25:27 Age [y:d:h:m:s]: 01:034:12:24:58
Block: 966074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285678 RingCT/type: yes/0
Extra: 01920708fba54b598dfb71b71a807c11b01a68c4d5c6fb7b868c815be64cdb5fcd02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03c3cacfb5dd7656220f91eb753de439bc1b3c6ff7371b1f4976e90857111ddd 0.600000000000 1425831 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": 966084, "vin": [ { "gen": { "height": 966074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03c3cacfb5dd7656220f91eb753de439bc1b3c6ff7371b1f4976e90857111ddd" } } ], "extra": [ 1, 146, 7, 8, 251, 165, 75, 89, 141, 251, 113, 183, 26, 128, 124, 17, 176, 26, 104, 196, 213, 198, 251, 123, 134, 140, 129, 91, 230, 76, 219, 95, 205, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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