Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42e6d80c1ca92fc413b59dc577a5ca1eefe3f0e7539aef68f4973b8147eadcc7

Tx prefix hash: b8a4df7d000369a36a59709b29ab42e4bafe2c8ce078432f644683c7dad41a51
Tx public key: b2cc2b676126bc8ec6672be638a7fbee4127523dfd4c5b3cd5a0482dab3ade1a
Timestamp: 1725374409 Timestamp [UCT]: 2024-09-03 14:40:09 Age [y:d:h:m:s]: 00:049:21:48:33
Block: 1102114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35715 RingCT/type: yes/0
Extra: 01b2cc2b676126bc8ec6672be638a7fbee4127523dfd4c5b3cd5a0482dab3ade1a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26efb9756017cac9fa07f634e7da9eb712da0200c486b53672f540f2d4314cf2 0.600000000000 1578421 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": 1102124, "vin": [ { "gen": { "height": 1102114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26efb9756017cac9fa07f634e7da9eb712da0200c486b53672f540f2d4314cf2" } } ], "extra": [ 1, 178, 204, 43, 103, 97, 38, 188, 142, 198, 103, 43, 230, 56, 167, 251, 238, 65, 39, 82, 61, 253, 76, 91, 60, 213, 160, 72, 45, 171, 58, 222, 26, 2, 17, 0, 0, 0, 4, 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