Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 667d5b1b37e4ac452fc4f3bd7f5c5f7b9463512c6bb082f542ff55d61ef91a1e

Tx prefix hash: 444c997637ad6b267fa2f54592d6e51edc3f173ca28bee50f2067ae4fce89736
Tx public key: 570ac8da9d4840175a91ee305ae0375e77c807696a4666fda24ad4e3ddeb5dc1
Timestamp: 1730100754 Timestamp [UCT]: 2024-10-28 07:32:34 Age [y:d:h:m:s]: 00:178:20:03:32
Block: 1141217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127664 RingCT/type: yes/0
Extra: 01570ac8da9d4840175a91ee305ae0375e77c807696a4666fda24ad4e3ddeb5dc10211000000058368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21c9e12b6b3e0cd48f19a8f5e45c655499e9ac80ed291753f6876a857a3bd98e 0.600000000000 1625024 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": 1141227, "vin": [ { "gen": { "height": 1141217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21c9e12b6b3e0cd48f19a8f5e45c655499e9ac80ed291753f6876a857a3bd98e" } } ], "extra": [ 1, 87, 10, 200, 218, 157, 72, 64, 23, 90, 145, 238, 48, 90, 224, 55, 94, 119, 200, 7, 105, 106, 70, 102, 253, 162, 74, 212, 227, 221, 235, 93, 193, 2, 17, 0, 0, 0, 5, 131, 104, 38, 109, 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