Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f800c35a54b116f5082e717d565fb0211d75646e76fe63a5db5b6ba9c2602c2e

Tx prefix hash: 0a972ced4562de96b3d9fe1f121b9ee733dbd58c6389cb8dd45a595a5d622e40
Tx public key: 9bd21368edc7f90b6da5e2d7e8524ff0331767e5831cac72d2d8037bd821259b
Timestamp: 1727983099 Timestamp [UCT]: 2024-10-03 19:18:19 Age [y:d:h:m:s]: 00:051:23:05:25
Block: 1123743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37117 RingCT/type: yes/0
Extra: 019bd21368edc7f90b6da5e2d7e8524ff0331767e5831cac72d2d8037bd821259b02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8da13fa7166c6f15ab6c554043f6c62b4f8439d6713e4848c8a186beca479e7 0.600000000000 1606278 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": 1123753, "vin": [ { "gen": { "height": 1123743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8da13fa7166c6f15ab6c554043f6c62b4f8439d6713e4848c8a186beca479e7" } } ], "extra": [ 1, 155, 210, 19, 104, 237, 199, 249, 11, 109, 165, 226, 215, 232, 82, 79, 240, 51, 23, 103, 229, 131, 28, 172, 114, 210, 216, 3, 123, 216, 33, 37, 155, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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