Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bd1612d759fdca867ba2cc34531be8edc9795ddc098640bbfeef5912ac0daa6

Tx prefix hash: 3f80eb1000a826bdcb1c0e9d86308ed6e4b7c7c975ef1003b4b0061e58a1a202
Tx public key: c79ff04f4c8fe920402abd342db63ab56b31acbdbae0680f159ae7eb5f1c40e3
Timestamp: 1574497451 Timestamp [UCT]: 2019-11-23 08:24:11 Age [y:d:h:m:s]: 05:038:07:11:44
Block: 15286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1170522 RingCT/type: yes/0
Extra: 01c79ff04f4c8fe920402abd342db63ab56b31acbdbae0680f159ae7eb5f1c40e3021100000001d50ca400000000000000000000

1 output(s) for total of 546.200408004000 dcy

stealth address amount amount idx
00: a01f0b94df06101dbf8804443d6bf0e4f83afe502c883c0763370e89d6044a51 546.200408004000 20334 of 0

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": 15296, "vin": [ { "gen": { "height": 15286 } } ], "vout": [ { "amount": 546200408004, "target": { "key": "a01f0b94df06101dbf8804443d6bf0e4f83afe502c883c0763370e89d6044a51" } } ], "extra": [ 1, 199, 159, 240, 79, 76, 143, 233, 32, 64, 42, 189, 52, 45, 182, 58, 181, 107, 49, 172, 189, 186, 224, 104, 15, 21, 154, 231, 235, 95, 28, 64, 227, 2, 17, 0, 0, 0, 1, 213, 12, 164, 0, 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