Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6e8402b750e80082a34cf1d3abf3c401e36b1d894483ded7b1c14d67a74cbd6

Tx prefix hash: 76e43ba6cda04d0137f3e20d6f76d3645cd37fdc3cc58145e7c4c0530199311d
Tx public key: ce7ba0a3f0e4db170c3a98392887cc2ccf57260d20937b756114397324f87ad8
Timestamp: 1694715903 Timestamp [UCT]: 2023-09-14 18:25:03 Age [y:d:h:m:s]: 01:204:03:36:18
Block: 848121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406997 RingCT/type: yes/0
Extra: 01ce7ba0a3f0e4db170c3a98392887cc2ccf57260d20937b756114397324f87ad8021100000003faf35c9c000000000000000000

1 output(s) for total of 0.950217697000 dcy

stealth address amount amount idx
00: 0456447e5c1d4fc7f1f9aeb5898bcf7616bbc82b29e63553387af8a4679a14d2 0.950217697000 1301705 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": 848131, "vin": [ { "gen": { "height": 848121 } } ], "vout": [ { "amount": 950217697, "target": { "key": "0456447e5c1d4fc7f1f9aeb5898bcf7616bbc82b29e63553387af8a4679a14d2" } } ], "extra": [ 1, 206, 123, 160, 163, 240, 228, 219, 23, 12, 58, 152, 57, 40, 135, 204, 44, 207, 87, 38, 13, 32, 147, 123, 117, 97, 20, 57, 115, 36, 248, 122, 216, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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