Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8093417994d6e857c996b63680c1cf84e5cf027b74b0d579bb739057d08e1b75

Tx prefix hash: be853cf842a7a69cd19d39bc698cb9384c0832dcb5dd17a1e7b4df55015784cc
Tx public key: 9901d3d8c88775ac4f0e1c49a7700bdf14d69ccff179c0928d5b9af169534f5f
Timestamp: 1723730113 Timestamp [UCT]: 2024-08-15 13:55:13 Age [y:d:h:m:s]: 00:100:17:47:20
Block: 1088483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72063 RingCT/type: yes/0
Extra: 019901d3d8c88775ac4f0e1c49a7700bdf14d69ccff179c0928d5b9af169534f5f021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c9eaad1cf6c88313f768c15550162c8aa71ef8670bb1a7db83f6ff700afca09 0.600000000000 1563100 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": 1088493, "vin": [ { "gen": { "height": 1088483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c9eaad1cf6c88313f768c15550162c8aa71ef8670bb1a7db83f6ff700afca09" } } ], "extra": [ 1, 153, 1, 211, 216, 200, 135, 117, 172, 79, 14, 28, 73, 167, 112, 11, 223, 20, 214, 156, 207, 241, 121, 192, 146, 141, 91, 154, 241, 105, 83, 79, 95, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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