Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2ebadc51c49f2423a6ad57eb77324e5c3a2f2f950abdc61d90aab81c3412d01

Tx prefix hash: 4066fa6c40e30369da97eae728ce089245d5e62f28b4b1911ab9509a19ba578c
Tx public key: 41195d6d772e1bfb3907d6711d359143b6ad945f15d7233c1c349087d8cd80a5
Timestamp: 1721260811 Timestamp [UCT]: 2024-07-18 00:00:11 Age [y:d:h:m:s]: 00:337:11:14:31
Block: 1068026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240981 RingCT/type: yes/0
Extra: 0141195d6d772e1bfb3907d6711d359143b6ad945f15d7233c1c349087d8cd80a502110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f6eb5564fa5f0e217d36d84a1cb5372c74c7819ca1e237f20c021daaa3a4720 0.600000000000 1539007 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": 1068036, "vin": [ { "gen": { "height": 1068026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f6eb5564fa5f0e217d36d84a1cb5372c74c7819ca1e237f20c021daaa3a4720" } } ], "extra": [ 1, 65, 25, 93, 109, 119, 46, 27, 251, 57, 7, 214, 113, 29, 53, 145, 67, 182, 173, 148, 95, 21, 215, 35, 60, 28, 52, 144, 135, 216, 205, 128, 165, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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