Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6646f9a1cfe640d95434a0683c52a4cef4708c93c1fde4e392a15cbce06b3c6

Tx prefix hash: 0bd2b1012e5932143b4a61c5f60b45f812ffde1dece089bbf2438fe47cf53e58
Tx public key: 6739c91eb9105fd7b3c765f442ebc469d04e3a84f65494a8938515e3bfd9662f
Timestamp: 1736610486 Timestamp [UCT]: 2025-01-11 15:48:06 Age [y:d:h:m:s]: 00:069:22:49:29
Block: 1195123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49770 RingCT/type: yes/0
Extra: 016739c91eb9105fd7b3c765f442ebc469d04e3a84f65494a8938515e3bfd9662f02110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0299f786e69a076148c1c2bfd8575dbbb1d8fa55888f391bfd7a6d0d61c420b2 0.600000000000 1681710 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": 1195133, "vin": [ { "gen": { "height": 1195123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0299f786e69a076148c1c2bfd8575dbbb1d8fa55888f391bfd7a6d0d61c420b2" } } ], "extra": [ 1, 103, 57, 201, 30, 185, 16, 95, 215, 179, 199, 101, 244, 66, 235, 196, 105, 208, 78, 58, 132, 246, 84, 148, 168, 147, 133, 21, 227, 191, 217, 102, 47, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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