Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b23bc7ea66047da69aa54f5d2b57d365fbaad255b338c05c735a43d1fdff1e9

Tx prefix hash: b05044fa827a276aadd5fae7565ed0cfffb124d29853f4ac8bff929971ab5080
Tx public key: 0fefee6df2f91a57e91e4f1deb53677a3fabdf408f4e2b125cefa3684645bfe5
Timestamp: 1722968346 Timestamp [UCT]: 2024-08-06 18:19:06 Age [y:d:h:m:s]: 01:062:21:46:44
Block: 1082160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303391 RingCT/type: yes/0
Extra: 010fefee6df2f91a57e91e4f1deb53677a3fabdf408f4e2b125cefa3684645bfe5021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eee456f4a3c2cc6fdee989073474a07880d19fb6a752b2dfb5cc46a33c006cc4 0.600000000000 1555985 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": 1082170, "vin": [ { "gen": { "height": 1082160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eee456f4a3c2cc6fdee989073474a07880d19fb6a752b2dfb5cc46a33c006cc4" } } ], "extra": [ 1, 15, 239, 238, 109, 242, 249, 26, 87, 233, 30, 79, 29, 235, 83, 103, 122, 63, 171, 223, 64, 143, 78, 43, 18, 92, 239, 163, 104, 70, 69, 191, 229, 2, 17, 0, 0, 0, 3, 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