Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 037b4a1ec30e34058fe38d839b69e9bc63a155b55d4c5862caa58ceda39740fe

Tx prefix hash: 5e52b5575d2cdab65291c16aebf8bc435d9437ee417e35d4e76ca8c8a8f76521
Tx public key: 4e247746aca3e8f000f939c0c5d741d7fc1215adeb2fbe282ebf4387c07f69fe
Timestamp: 1738624670 Timestamp [UCT]: 2025-02-03 23:17:50 Age [y:d:h:m:s]: 00:290:12:43:48
Block: 1211524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205410 RingCT/type: yes/0
Extra: 014e247746aca3e8f000f939c0c5d741d7fc1215adeb2fbe282ebf4387c07f69fe0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05f5e3ef843d4e750998ee813c258625e0b4a910f54781e85ca7c6abdbe30cca 0.600000000000 1698285 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": 1211534, "vin": [ { "gen": { "height": 1211524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05f5e3ef843d4e750998ee813c258625e0b4a910f54781e85ca7c6abdbe30cca" } } ], "extra": [ 1, 78, 36, 119, 70, 172, 163, 232, 240, 0, 249, 57, 192, 197, 215, 65, 215, 252, 18, 21, 173, 235, 47, 190, 40, 46, 191, 67, 135, 192, 127, 105, 254, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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