Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd91c751b1af5b944af7dcbb6c31f2281e75af79cbcde153dd309e9181570369

Tx prefix hash: 13b70ded794691e83815fde0a8bb9acd0bfb01391233d7f7f2c4604ff182bf04
Tx public key: 45cb6f820795f8e878023e9c7104fb1c8624d870b7d050ba4ada0ae547bd0db7
Timestamp: 1726395330 Timestamp [UCT]: 2024-09-15 10:15:30 Age [y:d:h:m:s]: 00:213:00:19:18
Block: 1110574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152078 RingCT/type: yes/0
Extra: 0145cb6f820795f8e878023e9c7104fb1c8624d870b7d050ba4ada0ae547bd0db702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3a75f978d39797d8b077faae438743145d4c2c64bad6778b65dce0c9dcdb5eb 0.600000000000 1589229 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": 1110584, "vin": [ { "gen": { "height": 1110574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3a75f978d39797d8b077faae438743145d4c2c64bad6778b65dce0c9dcdb5eb" } } ], "extra": [ 1, 69, 203, 111, 130, 7, 149, 248, 232, 120, 2, 62, 156, 113, 4, 251, 28, 134, 36, 216, 112, 183, 208, 80, 186, 74, 218, 10, 229, 71, 189, 13, 183, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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