Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e4ecf0481d992e02bb071ce346243d4694796a99b85c5dc59aa1ab6cbce9588

Tx prefix hash: f8c7b43d78852c89bf2078500887c279a5a773a1fe84a48812ed568b2e6ead19
Tx public key: 3dd207e4b51a77477c06b3a401eca69327d1b7a4ff35efd79f8455194cf2fee2
Timestamp: 1729742526 Timestamp [UCT]: 2024-10-24 04:02:06 Age [y:d:h:m:s]: 00:203:21:09:34
Block: 1138290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145534 RingCT/type: yes/0
Extra: 013dd207e4b51a77477c06b3a401eca69327d1b7a4ff35efd79f8455194cf2fee20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc44666fbf2b35c351764a1e5a83b66e5e28c383a10d507163d26cc30efdc1b5 0.600000000000 1621919 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": 1138300, "vin": [ { "gen": { "height": 1138290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc44666fbf2b35c351764a1e5a83b66e5e28c383a10d507163d26cc30efdc1b5" } } ], "extra": [ 1, 61, 210, 7, 228, 181, 26, 119, 71, 124, 6, 179, 164, 1, 236, 166, 147, 39, 209, 183, 164, 255, 53, 239, 215, 159, 132, 85, 25, 76, 242, 254, 226, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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