Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13bfa6bf80c13cf5e3bbd6de0e7edd8d7cd14fef18d993981effeed0ad7cafd9

Tx prefix hash: 870e417b30e399230a1496153459e8fca9a7c7ac271430ffdc792b85e4ff0b2b
Tx public key: 54ced01ff5c56b2d37d20432640b4a59aea8d319f7132fcc7eccb5b49569583d
Timestamp: 1705212126 Timestamp [UCT]: 2024-01-14 06:02:06 Age [y:d:h:m:s]: 01:065:04:26:22
Block: 934931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307712 RingCT/type: yes/0
Extra: 0154ced01ff5c56b2d37d20432640b4a59aea8d319f7132fcc7eccb5b49569583d0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93415a74aa5384704a9b1c43ed7915ea6c67946bcf7d6c9330823c3880d75436 0.600000000000 1392947 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": 934941, "vin": [ { "gen": { "height": 934931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93415a74aa5384704a9b1c43ed7915ea6c67946bcf7d6c9330823c3880d75436" } } ], "extra": [ 1, 84, 206, 208, 31, 245, 197, 107, 45, 55, 210, 4, 50, 100, 11, 74, 89, 174, 168, 211, 25, 247, 19, 47, 204, 126, 204, 181, 180, 149, 105, 88, 61, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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