Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c64bceba44feeaf35006192652ec83d1653354f48325cd65dceed017d718ccd7

Tx prefix hash: 1e9552962b82d4483c0db759e6f5748027a791afbcebadcd33cf362a74edcaba
Tx public key: 1b6abba5538e19a678c67c5f9736284c4af9a1ac44e19aec1f36a3e331ebf05c
Timestamp: 1718926435 Timestamp [UCT]: 2024-06-20 23:33:55 Age [y:d:h:m:s]: 00:271:23:53:15
Block: 1048650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194387 RingCT/type: yes/0
Extra: 011b6abba5538e19a678c67c5f9736284c4af9a1ac44e19aec1f36a3e331ebf05c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b19e30df48f0b6dd662922c7edb1e5d9f1d119b6245f9847590f15be5e85096b 0.600000000000 1518735 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": 1048660, "vin": [ { "gen": { "height": 1048650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b19e30df48f0b6dd662922c7edb1e5d9f1d119b6245f9847590f15be5e85096b" } } ], "extra": [ 1, 27, 106, 187, 165, 83, 142, 25, 166, 120, 198, 124, 95, 151, 54, 40, 76, 74, 249, 161, 172, 68, 225, 154, 236, 31, 54, 163, 227, 49, 235, 240, 92, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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