Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e8751c3118f02c054a76b067b5a69457db887b0042673017c3f7b5ba84b1cd9

Tx prefix hash: 091a2298557fb4037b6f0508dedb4957a0f2d94018c0c85417a15d98d03ab133
Tx public key: f05918c4d8af8c9a432785a36ac0ac451ea4d6f0faec3efa4f1651cff5188426
Timestamp: 1681503408 Timestamp [UCT]: 2023-04-14 20:16:48 Age [y:d:h:m:s]: 01:362:11:17:05
Block: 738644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520345 RingCT/type: yes/0
Extra: 01f05918c4d8af8c9a432785a36ac0ac451ea4d6f0faec3efa4f1651cff5188426021100000001faf35c9c000000000000000000

1 output(s) for total of 2.190614823000 dcy

stealth address amount amount idx
00: 9ed26e2d83bc8ac1d0a3f92c96ccdb45a86d8a57d4c7f26dffb0dc24df06fac6 2.190614823000 1185371 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": 738654, "vin": [ { "gen": { "height": 738644 } } ], "vout": [ { "amount": 2190614823, "target": { "key": "9ed26e2d83bc8ac1d0a3f92c96ccdb45a86d8a57d4c7f26dffb0dc24df06fac6" } } ], "extra": [ 1, 240, 89, 24, 196, 216, 175, 140, 154, 67, 39, 133, 163, 106, 192, 172, 69, 30, 164, 214, 240, 250, 236, 62, 250, 79, 22, 81, 207, 245, 24, 132, 38, 2, 17, 0, 0, 0, 1, 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