Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 579eec61869e98c6948c59249cdedead874f109507fe63a44f7ff6ed8cb8db75

Tx prefix hash: 8b21e35a62688e661cff72633b33cce7750ba115807a5f192bfdfe09af1d8fe0
Tx public key: 2f032ab6fd81606a7a385562aca4cc8adc3eb4a76cba15e3acf01c1c2b793f18
Timestamp: 1737312354 Timestamp [UCT]: 2025-01-19 18:45:54 Age [y:d:h:m:s]: 00:149:07:40:41
Block: 1200908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106448 RingCT/type: yes/0
Extra: 012f032ab6fd81606a7a385562aca4cc8adc3eb4a76cba15e3acf01c1c2b793f1802110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d49bc6ed4b3490d7505ff7cbf6ca3c12ef4dec34161e66da3f79efb4f09a2c17 0.600000000000 1687555 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": 1200918, "vin": [ { "gen": { "height": 1200908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d49bc6ed4b3490d7505ff7cbf6ca3c12ef4dec34161e66da3f79efb4f09a2c17" } } ], "extra": [ 1, 47, 3, 42, 182, 253, 129, 96, 106, 122, 56, 85, 98, 172, 164, 204, 138, 220, 62, 180, 167, 108, 186, 21, 227, 172, 240, 28, 28, 43, 121, 63, 24, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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