Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78e57fd30304d6e76ca3781c14c9acfdc4d8f81d7e632bf4cbc72f3e2e84080f

Tx prefix hash: 6fa8f0d09d80009509332fe0c27aae1a97ee6d3b3b7f104ec41100b1494fd815
Tx public key: 7cb50d33bc8188923b2d85440f5a8de1210bf0b08a41bb82429686fc74f0a687
Timestamp: 1734222648 Timestamp [UCT]: 2024-12-15 00:30:48 Age [y:d:h:m:s]: 00:109:13:36:46
Block: 1175371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78083 RingCT/type: yes/0
Extra: 017cb50d33bc8188923b2d85440f5a8de1210bf0b08a41bb82429686fc74f0a687021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3791f01c6c0617528b471011b3cd534dc359ebbc1cd83bbd9552301b6850d25b 0.600000000000 1661644 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": 1175381, "vin": [ { "gen": { "height": 1175371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3791f01c6c0617528b471011b3cd534dc359ebbc1cd83bbd9552301b6850d25b" } } ], "extra": [ 1, 124, 181, 13, 51, 188, 129, 136, 146, 59, 45, 133, 68, 15, 90, 141, 225, 33, 11, 240, 176, 138, 65, 187, 130, 66, 150, 134, 252, 116, 240, 166, 135, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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