Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e9f0cc3052247bbb22cf20e96aef9316efc6f104075581a56adfe49a63494e8

Tx prefix hash: ad86aa3c266341b85c5f9ee1655e023de5366fdd6427f16e98e5bba7ee6dce2a
Tx public key: 93a7e174dfaee9228c927b2b2ba7b085609456a597dd896971c574d3d8baf06f
Timestamp: 1724121057 Timestamp [UCT]: 2024-08-20 02:30:57 Age [y:d:h:m:s]: 00:232:12:23:18
Block: 1091722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166049 RingCT/type: yes/0
Extra: 0193a7e174dfaee9228c927b2b2ba7b085609456a597dd896971c574d3d8baf06f02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57a21c0fd0a7f376fb67faf9a0ccaaf680738bab5d4699c3b87aecf6e5dd5401 0.600000000000 1566355 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": 1091732, "vin": [ { "gen": { "height": 1091722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57a21c0fd0a7f376fb67faf9a0ccaaf680738bab5d4699c3b87aecf6e5dd5401" } } ], "extra": [ 1, 147, 167, 225, 116, 223, 174, 233, 34, 140, 146, 123, 43, 43, 167, 176, 133, 96, 148, 86, 165, 151, 221, 137, 105, 113, 197, 116, 211, 216, 186, 240, 111, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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