Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d7f7d29b622c40b03ab0893ad2affda26b36c964b29219aeb552b85737c8f96

Tx prefix hash: 2492faf0386d61cce9c853282e0f1324ce91c8b02971c60e43dace32b0105a7c
Tx public key: 08ed9bcf8270de64a66c08dc2be74f6bda1cf283923ff4b00ef6782280ccae40
Timestamp: 1649274864 Timestamp [UCT]: 2022-04-06 19:54:24 Age [y:d:h:m:s]: 02:342:00:44:27
Block: 474636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 764008 RingCT/type: yes/0
Extra: 0108ed9bcf8270de64a66c08dc2be74f6bda1cf283923ff4b00ef6782280ccae400211000000024da16a3a000000000000000000

1 output(s) for total of 16.418525201000 dcy

stealth address amount amount idx
00: 038a9aa138b24e3215a0a5d23dcb54b8c3d4c6177dfe5e965ed142247297a218 16.418525201000 894713 of 0

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": 474646, "vin": [ { "gen": { "height": 474636 } } ], "vout": [ { "amount": 16418525201, "target": { "key": "038a9aa138b24e3215a0a5d23dcb54b8c3d4c6177dfe5e965ed142247297a218" } } ], "extra": [ 1, 8, 237, 155, 207, 130, 112, 222, 100, 166, 108, 8, 220, 43, 231, 79, 107, 218, 28, 242, 131, 146, 63, 244, 176, 14, 246, 120, 34, 128, 204, 174, 64, 2, 17, 0, 0, 0, 2, 77, 161, 106, 58, 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