Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90e4f481677fa21152fb2b57d0bd51506534a5126feff756867ac7ca20f2ee53

Tx prefix hash: 42c601d7d9f85a3b662b07c468532d62dc98f6f9b5520b1b8ba7ec15133d10cb
Tx public key: 19d32f8727ce0c36d52a8cd8a40e152cdaac14472c46e9d6a72e76b560ac29b2
Timestamp: 1704099354 Timestamp [UCT]: 2024-01-01 08:55:54 Age [y:d:h:m:s]: 01:100:03:38:12
Block: 925717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332704 RingCT/type: yes/0
Extra: 0119d32f8727ce0c36d52a8cd8a40e152cdaac14472c46e9d6a72e76b560ac29b20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 311bbd27d83cb496959ed1e788b40a3e2f0fc29a4e8bf24839aec997cead3228 0.600000000000 1383483 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": 925727, "vin": [ { "gen": { "height": 925717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "311bbd27d83cb496959ed1e788b40a3e2f0fc29a4e8bf24839aec997cead3228" } } ], "extra": [ 1, 25, 211, 47, 135, 39, 206, 12, 54, 213, 42, 140, 216, 164, 14, 21, 44, 218, 172, 20, 71, 44, 70, 233, 214, 167, 46, 118, 181, 96, 172, 41, 178, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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