Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e80a4be4701df511f39b4f7c4e862c4388f5a6844fa6e06c53affe889ee034d6

Tx prefix hash: c312eb7e5004e10bb880b1a7485b1724dd1684ac8db2451ce25a6e8505c161cd
Tx public key: 7c2fc040f4a391f64f14a4d007d158484da691934aa46949d5ad38117bf1e8e8
Timestamp: 1728379840 Timestamp [UCT]: 2024-10-08 09:30:40 Age [y:d:h:m:s]: 01:109:23:04:54
Block: 1127030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336881 RingCT/type: yes/0
Extra: 017c2fc040f4a391f64f14a4d007d158484da691934aa46949d5ad38117bf1e8e802110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62227a36ff54cc6bb1d0fd84efb59338b79fe2f0fb7a3379dae2c095bc28bb6f 0.600000000000 1609829 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": 1127040, "vin": [ { "gen": { "height": 1127030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62227a36ff54cc6bb1d0fd84efb59338b79fe2f0fb7a3379dae2c095bc28bb6f" } } ], "extra": [ 1, 124, 47, 192, 64, 244, 163, 145, 246, 79, 20, 164, 208, 7, 209, 88, 72, 77, 166, 145, 147, 74, 164, 105, 73, 213, 173, 56, 17, 123, 241, 232, 232, 2, 17, 0, 0, 0, 10, 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