Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8f81c40bfe9cfc550be502c59e4e432644e9f51fef4e5e39ef188ab28fbdcf8

Tx prefix hash: 682d142f89b9a3a35e4e7ebdce564abfa967f0acf638e10bc4ccc9bffc202e18
Tx public key: 0c590a811602546194d1c731b8799a614c1a61d7b880ad246029b08519a10590
Timestamp: 1738579501 Timestamp [UCT]: 2025-02-03 10:45:01 Age [y:d:h:m:s]: 00:341:03:34:27
Block: 1211147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241666 RingCT/type: yes/0
Extra: 010c590a811602546194d1c731b8799a614c1a61d7b880ad246029b08519a105900211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98a510ef17dd08994268d3d22db4ac6f11fdb7e9c0a14c485fbc6268c0b59c58 0.600000000000 1697906 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": 1211157, "vin": [ { "gen": { "height": 1211147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98a510ef17dd08994268d3d22db4ac6f11fdb7e9c0a14c485fbc6268c0b59c58" } } ], "extra": [ 1, 12, 89, 10, 129, 22, 2, 84, 97, 148, 209, 199, 49, 184, 121, 154, 97, 76, 26, 97, 215, 184, 128, 173, 36, 96, 41, 176, 133, 25, 161, 5, 144, 2, 17, 0, 0, 0, 5, 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