Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bffd2405b04f2cb46b3cd73826003dfd614be2eb078138c8103fab80fa0376c

Tx prefix hash: 41df39741e2a18f3471298051e5456ab9dcb9b8bac77b683b711f878c47dc82a
Tx public key: 4a1eb2ebb1c6447e3b0f3bcd5bb1cacf3edf1b3bd1fce4e52370a1ed10ea8b88
Timestamp: 1581545759 Timestamp [UCT]: 2020-02-12 22:15:59 Age [y:d:h:m:s]: 05:011:18:56:50
Block: 63743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161177 RingCT/type: yes/0
Extra: 014a1eb2ebb1c6447e3b0f3bcd5bb1cacf3edf1b3bd1fce4e52370a1ed10ea8b88021100000006fe8cc51f000000000000000000

1 output(s) for total of 377.392958629000 dcy

stealth address amount amount idx
00: e74a9e9696e26240340921d6373cee12932ae947c934b2433b9652984f503548 377.392958629000 117494 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": 63753, "vin": [ { "gen": { "height": 63743 } } ], "vout": [ { "amount": 377392958629, "target": { "key": "e74a9e9696e26240340921d6373cee12932ae947c934b2433b9652984f503548" } } ], "extra": [ 1, 74, 30, 178, 235, 177, 198, 68, 126, 59, 15, 59, 205, 91, 177, 202, 207, 62, 223, 27, 59, 209, 252, 228, 229, 35, 112, 161, 237, 16, 234, 139, 136, 2, 17, 0, 0, 0, 6, 254, 140, 197, 31, 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