Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00430e53ae468880089ebb99f1c90187280bfed191f946178fcdc6b932bf786d

Tx prefix hash: 4316d2a1e22b87873d4ae142b440b45b24c56b6d295b33a29a4702dfa57e0f97
Tx public key: 4c50ebce9bcbf8bbe809fd0aff2f9591218bdec31e04894be63f924acd28ad39
Timestamp: 1608431800 Timestamp [UCT]: 2020-12-20 02:36:40 Age [y:d:h:m:s]: 04:009:12:24:04
Block: 165553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1019524 RingCT/type: yes/0
Extra: 014c50ebce9bcbf8bbe809fd0aff2f9591218bdec31e04894be63f924acd28ad390211000000294ea414e5000000000000000000

1 output(s) for total of 173.562085127000 dcy

stealth address amount amount idx
00: 2ee29a813ed288a29171c86e0d6e3c5c58791a9873b1ab6f3040ed58b35b6321 173.562085127000 301458 of 0

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": 165563, "vin": [ { "gen": { "height": 165553 } } ], "vout": [ { "amount": 173562085127, "target": { "key": "2ee29a813ed288a29171c86e0d6e3c5c58791a9873b1ab6f3040ed58b35b6321" } } ], "extra": [ 1, 76, 80, 235, 206, 155, 203, 248, 187, 232, 9, 253, 10, 255, 47, 149, 145, 33, 139, 222, 195, 30, 4, 137, 75, 230, 63, 146, 74, 205, 40, 173, 57, 2, 17, 0, 0, 0, 41, 78, 164, 20, 229, 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