Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9259b650ea36252b0829ebe5ed67ac5745d4080ca21e0e9db038bcf8af0b602

Tx prefix hash: f34c9026cedb4bd07501859c4b71fd754d8824cf1e76df4993a8168f234799cc
Tx public key: 0c67c377c52bc38842631c5376007c64a46f4df3a6f5918635c653d981ad9f4e
Timestamp: 1706713785 Timestamp [UCT]: 2024-01-31 15:09:45 Age [y:d:h:m:s]: 01:076:14:34:47
Block: 947387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315833 RingCT/type: yes/0
Extra: 010c67c377c52bc38842631c5376007c64a46f4df3a6f5918635c653d981ad9f4e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e2ca9a15d69b06b6f8a29041b2c5a31b19a60e8c1671f9d9cf53ba3b06d27b2 0.600000000000 1405735 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": 947397, "vin": [ { "gen": { "height": 947387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e2ca9a15d69b06b6f8a29041b2c5a31b19a60e8c1671f9d9cf53ba3b06d27b2" } } ], "extra": [ 1, 12, 103, 195, 119, 197, 43, 195, 136, 66, 99, 28, 83, 118, 0, 124, 100, 164, 111, 77, 243, 166, 245, 145, 134, 53, 198, 83, 217, 129, 173, 159, 78, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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