Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ab4c151e782334e81b18f3107f1b9e73106e1e119f263d6c58ddb54f9776923

Tx prefix hash: 5ef1ea2ad5e1bf7d7e09d848994bf1a73c43639ffce6fe4cff437cc894ab9342
Tx public key: d6f51db915b40925cc25e4a3c9150761a0ab07337b573130d5fc38ec3b9bf5ff
Timestamp: 1729046543 Timestamp [UCT]: 2024-10-16 02:42:23 Age [y:d:h:m:s]: 00:000:18:49:57
Block: 1132573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548 RingCT/type: yes/0
Extra: 01d6f51db915b40925cc25e4a3c9150761a0ab07337b573130d5fc38ec3b9bf5ff02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e04f8fa3bffb174452847d32aa24e812533a16df85d5043a9dae85f5e9f91032 0.600000000000 1615520 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": 1132583, "vin": [ { "gen": { "height": 1132573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e04f8fa3bffb174452847d32aa24e812533a16df85d5043a9dae85f5e9f91032" } } ], "extra": [ 1, 214, 245, 29, 185, 21, 180, 9, 37, 204, 37, 228, 163, 201, 21, 7, 97, 160, 171, 7, 51, 123, 87, 49, 48, 213, 252, 56, 236, 59, 155, 245, 255, 2, 17, 0, 0, 0, 3, 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