Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6b35ce57565f54f6c94628e8782c8d10d929822de785b9c7605999c18678e2e

Tx prefix hash: 0170a062bf47d137532c553a4fe9e4320d4a3679094ee780284d1fe92fcc13c1
Tx public key: 417c1df5d708a4e60bb49cf64095dc06ad19cf86acc420a87309474633394c8a
Timestamp: 1701837176 Timestamp [UCT]: 2023-12-06 04:32:56 Age [y:d:h:m:s]: 01:140:02:12:14
Block: 906970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361289 RingCT/type: yes/0
Extra: 01417c1df5d708a4e60bb49cf64095dc06ad19cf86acc420a87309474633394c8a021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.606501476000 dcy

stealth address amount amount idx
00: 8b51b1fa4663ff0d15ec899dd4e16d5f9df52ae8104b85c84f18cd88b2ba9b6a 0.606501476000 1363933 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": 906980, "vin": [ { "gen": { "height": 906970 } } ], "vout": [ { "amount": 606501476, "target": { "key": "8b51b1fa4663ff0d15ec899dd4e16d5f9df52ae8104b85c84f18cd88b2ba9b6a" } } ], "extra": [ 1, 65, 124, 29, 245, 215, 8, 164, 230, 11, 180, 156, 246, 64, 149, 220, 6, 173, 25, 207, 134, 172, 196, 32, 168, 115, 9, 71, 70, 51, 57, 76, 138, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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