Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00e8ccef44995222eefbb820ddef231746efe3ecec7b8a0434c7150702b3eafb

Tx prefix hash: 9032beb7cda37bcd7df1d486a24edbda2312d2d3991f824288edafb61d95ac69
Tx public key: b5ee1a5dccddf7258aca951bd6cf222c993529ae54daa5f20fd98506d5b85cb0
Timestamp: 1716179551 Timestamp [UCT]: 2024-05-20 04:32:31 Age [y:d:h:m:s]: 00:323:04:23:40
Block: 1025888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230978 RingCT/type: yes/0
Extra: 01b5ee1a5dccddf7258aca951bd6cf222c993529ae54daa5f20fd98506d5b85cb00211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 490baa790b5a9e72d584d5db4ee0f72f16ca2b07c3d992b21aaaf8aad1aa583d 0.600000000000 1492667 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": 1025898, "vin": [ { "gen": { "height": 1025888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "490baa790b5a9e72d584d5db4ee0f72f16ca2b07c3d992b21aaaf8aad1aa583d" } } ], "extra": [ 1, 181, 238, 26, 93, 204, 221, 247, 37, 138, 202, 149, 27, 214, 207, 34, 44, 153, 53, 41, 174, 84, 218, 165, 242, 15, 217, 133, 6, 213, 184, 92, 176, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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