Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bac738e9c2c4e45f4fda50f3fe0c852b70308c5a024096e7ba4a854d8bc2fbd

Tx prefix hash: 3a83d8e9aa91f44f867adba56a6b7992c386ea4bce0eb25983cc228211c4e0e1
Tx public key: e8c09922e87c0c5ce6e04b2533274b343affb2179f2d46a1bf692b1d4ee52753
Timestamp: 1714290690 Timestamp [UCT]: 2024-04-28 07:51:30 Age [y:d:h:m:s]: 00:305:15:05:48
Block: 1010220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218454 RingCT/type: yes/0
Extra: 01e8c09922e87c0c5ce6e04b2533274b343affb2179f2d46a1bf692b1d4ee527530211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c56ff0214d281cbed79c52f52aadb97aeb6d13d48c4ffc956cb641cfbe9356a 0.600000000000 1472110 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": 1010230, "vin": [ { "gen": { "height": 1010220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c56ff0214d281cbed79c52f52aadb97aeb6d13d48c4ffc956cb641cfbe9356a" } } ], "extra": [ 1, 232, 192, 153, 34, 232, 124, 12, 92, 230, 224, 75, 37, 51, 39, 75, 52, 58, 255, 178, 23, 159, 45, 70, 161, 191, 105, 43, 29, 78, 229, 39, 83, 2, 17, 0, 0, 0, 3, 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