Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0458e9a2f46ef01cee076e02ec17c2425d91ab7f4f6ee5f8baca5b82701b985

Tx prefix hash: 2ecb67c4cf8538caa25c93c85f3b22f4aab5aecb07020fe1ce6219fbd5c17915
Tx public key: 16a326166ee91ba0e4c3a2b7917cd19190a0941ff8681cb3c1983adf0e5c75fa
Timestamp: 1718200825 Timestamp [UCT]: 2024-06-12 14:00:25 Age [y:d:h:m:s]: 00:169:06:18:19
Block: 1042652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121134 RingCT/type: yes/0
Extra: 0116a326166ee91ba0e4c3a2b7917cd19190a0941ff8681cb3c1983adf0e5c75fa02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b6bbdcc523c08701cb2da4643cea7e63f2e6a50724d6ca91e591ea72905d5e6 0.600000000000 1511615 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": 1042662, "vin": [ { "gen": { "height": 1042652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b6bbdcc523c08701cb2da4643cea7e63f2e6a50724d6ca91e591ea72905d5e6" } } ], "extra": [ 1, 22, 163, 38, 22, 110, 233, 27, 160, 228, 195, 162, 183, 145, 124, 209, 145, 144, 160, 148, 31, 248, 104, 28, 179, 193, 152, 58, 223, 14, 92, 117, 250, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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