Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cebd45203c1a547c626e0ce1421852159f7af303f7e6ad0d52539a8791fd819

Tx prefix hash: b5fd12fcfddc21055e9229d16aeb77269b35d43259c6bb7d5636f48a1892e027
Tx public key: 2c301859d90cb677a471fc9b095b815d7078a000e49a8f4f7c2754d67ef0d382
Timestamp: 1725301333 Timestamp [UCT]: 2024-09-02 18:22:13 Age [y:d:h:m:s]: 00:083:09:29:31
Block: 1101502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59637 RingCT/type: yes/0
Extra: 012c301859d90cb677a471fc9b095b815d7078a000e49a8f4f7c2754d67ef0d382021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb44fe5aad59c98c1a460ba1a8de9d35798c360df730c0e735b15be15185cec3 0.600000000000 1577577 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": 1101512, "vin": [ { "gen": { "height": 1101502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb44fe5aad59c98c1a460ba1a8de9d35798c360df730c0e735b15be15185cec3" } } ], "extra": [ 1, 44, 48, 24, 89, 217, 12, 182, 119, 164, 113, 252, 155, 9, 91, 129, 93, 112, 120, 160, 0, 228, 154, 143, 79, 124, 39, 84, 214, 126, 240, 211, 130, 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