Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c3e32cce10b53006510c9e3b757976932b1d7a71e53a868ba533c3b01ed76eb

Tx prefix hash: 6f75a222c486c2c9ba1d6ca18bec26ace949d59b02b89d4e53cf1c4921f4c56f
Tx public key: 1707aed88e0fbe00dcc09a419df6f5afc3111728a737e8ac3a495eda37bf9aae
Timestamp: 1730581145 Timestamp [UCT]: 2024-11-02 20:59:05 Age [y:d:h:m:s]: 00:221:17:11:06
Block: 1145190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158308 RingCT/type: yes/0
Extra: 011707aed88e0fbe00dcc09a419df6f5afc3111728a737e8ac3a495eda37bf9aae0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7c4432c650242d44d952ce2f1fc405b95445e020120af65468645b3c07137c9 0.600000000000 1629587 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": 1145200, "vin": [ { "gen": { "height": 1145190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7c4432c650242d44d952ce2f1fc405b95445e020120af65468645b3c07137c9" } } ], "extra": [ 1, 23, 7, 174, 216, 142, 15, 190, 0, 220, 192, 154, 65, 157, 246, 245, 175, 195, 17, 23, 40, 167, 55, 232, 172, 58, 73, 94, 218, 55, 191, 154, 174, 2, 17, 0, 0, 0, 2, 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