Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e78ba58cbe46fbe56d232c278064472522b0f65c9e0e718da4c7591dbbd80a6a

Tx prefix hash: 12350853214f7d2b9e7be73c0277bea2edb7d43013d5a9f23b678e6b88ba4281
Tx public key: e5f482375b46314d651da2a63d374e196ee5635c927b043ef8d067d110a4b866
Timestamp: 1722440973 Timestamp [UCT]: 2024-07-31 15:49:33 Age [y:d:h:m:s]: 00:175:22:41:53
Block: 1077787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125842 RingCT/type: yes/0
Extra: 01e5f482375b46314d651da2a63d374e196ee5635c927b043ef8d067d110a4b866021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4164f4ef8dddc970b6c495c17317e7a84a144de7eb877aac3fd0d6aee59cfe40 0.600000000000 1550342 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": 1077797, "vin": [ { "gen": { "height": 1077787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4164f4ef8dddc970b6c495c17317e7a84a144de7eb877aac3fd0d6aee59cfe40" } } ], "extra": [ 1, 229, 244, 130, 55, 91, 70, 49, 77, 101, 29, 162, 166, 61, 55, 78, 25, 110, 229, 99, 92, 146, 123, 4, 62, 248, 208, 103, 209, 16, 164, 184, 102, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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