Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 283c60113c1a88246428880aa11d6bc8dd14147a45e852d0e4093e6c104e2852

Tx prefix hash: 5b7898da95313e1e607bec0ddc10bb411bc647b1c73be87e1e67989ef9d1364c
Tx public key: b3175306f5bcb5e51ff087b7b240b84cf66283ede4a53850a946f2aeae4754b3
Timestamp: 1722142285 Timestamp [UCT]: 2024-07-28 04:51:25 Age [y:d:h:m:s]: 00:249:18:30:40
Block: 1075315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178414 RingCT/type: yes/0
Extra: 01b3175306f5bcb5e51ff087b7b240b84cf66283ede4a53850a946f2aeae4754b3021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91dd45c31ed4080cf48c52d65a25c41c30c3e1fda7e05265850034ab6e458319 0.600000000000 1547840 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": 1075325, "vin": [ { "gen": { "height": 1075315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91dd45c31ed4080cf48c52d65a25c41c30c3e1fda7e05265850034ab6e458319" } } ], "extra": [ 1, 179, 23, 83, 6, 245, 188, 181, 229, 31, 240, 135, 183, 178, 64, 184, 76, 246, 98, 131, 237, 228, 165, 56, 80, 169, 70, 242, 174, 174, 71, 84, 179, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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