Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41769d5a2b879771c3e132024ddc15bfc7ed23787bad91203c5efcd66642b2b2

Tx prefix hash: 68c185aea39ff84f3b655338b311ec4e299023106a4c1f4639f5f50fc1cf52b0
Tx public key: f5c9458dabef9102041cd97af2b707cc14d566a7a7b04f94c8ad896b2fe5f8e0
Timestamp: 1723764406 Timestamp [UCT]: 2024-08-15 23:26:46 Age [y:d:h:m:s]: 00:245:01:23:21
Block: 1088766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175013 RingCT/type: yes/0
Extra: 01f5c9458dabef9102041cd97af2b707cc14d566a7a7b04f94c8ad896b2fe5f8e0021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a26684ad425105ae80f5261a71501b50e1fb616d0b081b2a331e85612d0299e8 0.600000000000 1563385 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": 1088776, "vin": [ { "gen": { "height": 1088766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a26684ad425105ae80f5261a71501b50e1fb616d0b081b2a331e85612d0299e8" } } ], "extra": [ 1, 245, 201, 69, 141, 171, 239, 145, 2, 4, 28, 217, 122, 242, 183, 7, 204, 20, 213, 102, 167, 167, 176, 79, 148, 200, 173, 137, 107, 47, 229, 248, 224, 2, 17, 0, 0, 0, 5, 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