Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b491516034e7f137fd44e60630c99604807cacf59fbbe825e9c03ec802676ce

Tx prefix hash: 92c1e887d12a2601298963db4b909505758a3eb5374e379fda44697201d38677
Tx public key: 28ea0c8d8e860fbf0dd8977fea0c8e465ed5f361c21a8b67f45e73c34e1f505c
Timestamp: 1727191922 Timestamp [UCT]: 2024-09-24 15:32:02 Age [y:d:h:m:s]: 00:061:10:10:48
Block: 1117190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43884 RingCT/type: yes/0
Extra: 0128ea0c8d8e860fbf0dd8977fea0c8e465ed5f361c21a8b67f45e73c34e1f505c021100000012e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5696c89f9a2a5e05fc8d834a12f91b10af099eea8473adb510f776dd407c0f71 0.600000000000 1597933 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": 1117200, "vin": [ { "gen": { "height": 1117190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5696c89f9a2a5e05fc8d834a12f91b10af099eea8473adb510f776dd407c0f71" } } ], "extra": [ 1, 40, 234, 12, 141, 142, 134, 15, 191, 13, 216, 151, 127, 234, 12, 142, 70, 94, 213, 243, 97, 194, 26, 139, 103, 244, 94, 115, 195, 78, 31, 80, 92, 2, 17, 0, 0, 0, 18, 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