Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87780f48c3a659159d46f7d1b801529ea0bccb03434f0f5a7ab0f78b3d13e327

Tx prefix hash: f64d5ef7c1574f98860d680f9c309d62fb02e1477d191288c44a1a9de884eed8
Tx public key: 2bdf4d16d4787ad80e0860b2a93cd12fb9be6544ab39696f88b72aa99442eb68
Timestamp: 1709527291 Timestamp [UCT]: 2024-03-04 04:41:31 Age [y:d:h:m:s]: 01:248:18:34:40
Block: 970740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436516 RingCT/type: yes/0
Extra: 012bdf4d16d4787ad80e0860b2a93cd12fb9be6544ab39696f88b72aa99442eb680211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 038bc8179fe7e4fbfcb2b51824b307d47ad2e89c37221932b8e3415cd6467c07 0.600000000000 1430601 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": 970750, "vin": [ { "gen": { "height": 970740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "038bc8179fe7e4fbfcb2b51824b307d47ad2e89c37221932b8e3415cd6467c07" } } ], "extra": [ 1, 43, 223, 77, 22, 212, 120, 122, 216, 14, 8, 96, 178, 169, 60, 209, 47, 185, 190, 101, 68, 171, 57, 105, 111, 136, 183, 42, 169, 148, 66, 235, 104, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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