Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46c00ee2823327cb33b222168913d67f8a1dd97da34ee9b7076d09d47f6347c6

Tx prefix hash: dec80b84e7d732270e6a079ba97642354f8edaa30612224622719e46ff7f26cb
Tx public key: 71cd182416cb0194ea5dfdda21bbd5e8e5b32e44cf2f2cff1ce24f60469033c2
Timestamp: 1722364049 Timestamp [UCT]: 2024-07-30 18:27:29 Age [y:d:h:m:s]: 01:100:04:54:03
Block: 1077152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330105 RingCT/type: yes/0
Extra: 0171cd182416cb0194ea5dfdda21bbd5e8e5b32e44cf2f2cff1ce24f60469033c2021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56c6084d20c2f9b5f4594d79b5a8af3258cd06cd9d066655f23b051bd6add8e5 0.600000000000 1549697 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": 1077162, "vin": [ { "gen": { "height": 1077152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56c6084d20c2f9b5f4594d79b5a8af3258cd06cd9d066655f23b051bd6add8e5" } } ], "extra": [ 1, 113, 205, 24, 36, 22, 203, 1, 148, 234, 93, 253, 218, 33, 187, 213, 232, 229, 179, 46, 68, 207, 47, 44, 255, 28, 226, 79, 96, 70, 144, 51, 194, 2, 17, 0, 0, 0, 9, 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